3 avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
5 date="2023-04-25T18:45:58Z"
7 Just for completeness -- do we really need a new type of record for this? In immediate use case which is [in the heart of the path escaping change discussion](https://git-annex.branchable.com/bugs/started_to_escape_characters_in_the_output/) let's consider other commands. E.g. `addurl` already reports `--json-errors` just fine in a similar case
10 ❯ git annex addurl --json --json-error-messages '\e[31mfo\o\e[0m'
11 {\"command\":\"addurl\",\"error-messages\":[\"git-annex: bad url \\e[31mfo\\o\\e[0m\"],\"file\":null,\"input\":[\"\\e[31mfo\\o\\e[0m\"],\"success\":false}
15 so why just not to make `add`'s
18 ❯ git annex add --json --json-error-messages '\e[31mfo\o\e[0m'
19 git-annex: \e[31mfo\o\e[0m not found
26 {\"command\":\"add\",\"error-messages\":[\"git-annex: \\e[31mfo\\o\\e[0m not found\"],\"file\":null,\"input\":[\"\\e[31mfo\\o\\e[0m\"],\"success\":false}
30 or if you want to expand with unambigous ID:
33 {\"command\":\"add\",\"error-messages\":[\"git-annex: \\e[31mfo\\o\\e[0m not found\"],\"file\":null,\"input\":[\"\\e[31mfo\\o\\e[0m\"],\"success\":false, \"errorid\": \"NOT_FOUND\"}
36 or alike without requiring some new CLI option?